<h2>Why is this an issue?</h2>
<p>If an exception is already being thrown within the <code>try</code> block or caught in a <code>catch</code> block, throwing another exception in
the <code>finally</code> block will override the original exception. This means that the original exception’s message and stack trace will be lost,
potentially making it challenging to diagnose and troubleshoot the root cause of the problem.</p>
<pre data-diff-id="1" data-diff-type="noncompliant">
Try
    ' Some work which end up throwing an exception
    Throw New ArgumentException()
Finally
    ' Cleanup
    Throw New InvalidOperationException() ' Noncompliant: will mask the ArgumentException
End Try
</pre>
<pre data-diff-id="1" data-diff-type="compliant">
Try
    ' Some work which end up throwing an exception
    Throw New ArgumentException()
Finally
    ' Cleanup without throwing
End Try
</pre>
<h2>Resources</h2>
<h3>Documentation</h3>
<ul>
  <li> <a href="https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/exceptions/">Exceptions and Exception Handling</a> </li>
  <li> <a href="https://learn.microsoft.com/en-us/dotnet/standard/exceptions/how-to-use-finally-blocks">Finally blocks</a> </li>
  <li> <a href="https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/exceptions/how-to-execute-cleanup-code-using-finally">How to execute
  cleanup code using finally</a> </li>
</ul>

